Maybe a stupid question, but have you installed the HDMI adapter that connects the Raspberry HDMI to the HDMI of the Game Hat? You probably had to remove it to install the Raspberry to the Game Hat, but after doing so you need to put it back!

@danield420 well the black screen could be a bad rom or possibly a missing bios file. Sure there are other factors for the balck screen i'm still learning myself. This RetroPie Github page has helped me so much https://github.com/RetroPie/RetroPie-Setup/wiki/Supported-Systems .

Or make another topic and i'm sure someone can help you solve the problem if you didn't already on your own.

@dankcushions Thank you for the reply. I figured it was something like that.

What is the best way to delete all core overrides at once? Using the retoarch menu or by deleting a specific config file?

Thanks for your help.

@mitu It was definitely a storage issue.

I deleted the Skyscraper cache, and it freed up over 40gb of storage!

The issue is now gone.

Thanks for your help!

Does your monitor's HDMI port works ? Can you connect it to another device to see if it receives and displays HDMI video ?
Try playing with the config_hdmi_boostconfiguration parameter in the config.txt file. From Video options in config.txt:

config_hdmi_boost
Configures the signal strength of the HDMI interface. The default value is 0 and the maximum is 11.

The default value for the original Model B and A is 2. The default value for the Model B+ and all later models is 5.

If you are seeing HDMI issues (speckling, interference) then try 7. Very long HDMI cables may need up to 11, but values this high should not be used unless absolutely necessary.

@quicksilver I just realized my mistake thanks! Only wish I noticed hours ago!

I was actually wrong it started up again but when i connected a power supply to my hdmi av connector it stopped and has been good since i think it is a power issue and using overscan must draw less power so thats why it seemed better

@vinz2k It depends - do you hear the audio from the video ? Do your gamelist also have empty video tags ? I think the fix should be in the 2.8.3rp version, so maybe you're experiencing another problem.

@cyperghost said in Just updated retropie -- now screensaver doesn't work:

What was the version of ES before you updated?

OOh, no idea what the old version was. Probably from September 2018 when I last updated.

@pjft said in Just updated retropie -- now screensaver doesn't work:

probably more related to your playlists and scraping that have added other video tags?

Aaaaah, yes, that's a good idea!! I did do a new scrape for one system using Skyscraper rather than using the built-in scrapers. That would explain why is seems to be "looking" for a video, but not finding it -- except that one day, that one time, where it DID find it and it worked as expected. Because Skyscraper adds the <video /> tag to each game.

I'll delete every instance of <video /> and see if that works.

OMG, yes, it WORKS!
Using my original 'dummy game'

<game> <video>/home/pi/RetroPie/screensavers/screensaver_01.mp4</video> </game>

put into a gamelist.xml

Thanks guys!!!! Now my retro pie is complete!!!

Man, why didn't I think of that in the first place?

@zuuzuu
Hello guys.
I've encountered the exact same problem with ALL f1 games for ps1. 2001 version is unplayable, and others get stuck in the first screen, right after "ea games challenge everything..." Did you guys manage to fix or at least identify the problem?
I tried also an android emulator and got the exact same result.... That's sad, I have plenty of ps1 games on my raspberry, and they all work great...

@mitu said in only shows picture when HDMI is connected at startup?:

It's normal - for some TVs - https://kodi.wiki/view/Raspberry_Pi_FAQ#TV_is_not_detected_unless_powered_on_first.

Thanks for the link @mitu! This happened to me too once. I had to unplug the pi as got no display on my TV (luckily my SD card survived the ordeal!). Great to know there is a solution (other than just remembering to turn on my TV first).

@grant2258 thanks, i will try it.

They do have a discord, you could try there. http://odroidarena.com/ link should be on the right hand side of the page.

@phoenixjedi For a PC, with enough CPU, it won't affect the performance. You're free to use both options and see the difference, if any. Note that RetroArch defaults to not activate this option by default on Pc builld.

@bejhan this didnt fix the black screen issue for me with kodi 18.1 on this vizio vo400e tv. This did fix an issue with kodi 18.1 where the screen was crazy zoomed in and the only way to fix it was to minimize the screen and then maximize it again on an lg oled c6.
On the vizio tv that i am having issues with now if i just power the tv off then on again it works fine till i go back to the retropie menu and then thats a black screen. Same thing happens if I switch film mode off then kodi appears but then when you exit the retropie menu is a black screen. Same thing happens when you switch inputs on the tv from hdmi 1 (where pie is connected) to something else then back to hdmi 1 and once again when you exit the retropie menu is black screen until you do 1 of the methods i mentioned above. So what is kodi on launch (and exit) doing that is making the tv black screen that nothing else installed in retropie is doing. For example I have pixel desktop (lxde) installed under ports also and a bunch of emulators. Everything else but kodi launches and exits fine.

@mitu na all roms are running on the sd card, 32GB sandisk. I have a few of them that I cycle through during updates etc. All of them have shown the same behavior. I haven't changed default config.txt.

I'm using an LCD monitor with hdmi, not sure if that was the screen question :)

Also the map message only happens with Galaga so far, Berzerk does not show that it just completely freezes, screen does not go black like Galaga does.

@mitu

Thanks man, it works. You are awesome 😊

I've read about Wayland fixing things, and it seems like it fixed the issue in my case. Installed KDE, enabled Wayland and it seems to work great now :)

@EpicFury Did you hit the Tab key in AM like @Walker843 suggested?

Do I understand you correctly that you mean by "find a way back to ES" to boot into ES instead of AM? I don't know Floob's image, but since it's based on Retropie, the frontend to start at boot should be in the file /opt/retropie/configs/all/autostart.sh. To boot into ES, the file should (only) contain this line:

emulationstation #auto

I would recommend to backup the file first, though.